-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add daily vulnerability scan #100
Conversation
.github/workflows/daily-vul-scan.yml
Outdated
issues: write | ||
|
||
jobs: | ||
build: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I feel the job should be separated more as not only building here.
Such as scanning and making an issue.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As you suggested, it seemed like a good idea to separate the jobs.
However, upon consideration of the following points, I concluded that processing the trivy results within the same job would be more efficient than writing them out as a string and sharing across different jobs.
- The output of
aquasecurity/trivy-action@master
is specified by file. - The input specification for
JasonEtco/create-an-issue@v2
isfilename
.
Consequently, I decided to only change the job name, instead of separating the jobs.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OK, I understand it's tough to separate jobs.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Description
I have updated three files for daily vulnerability scan.
daily-vul-scan.yml
README.md
trivy-results.tpl
1.
daily-vul-scan.yml
Add daily vulnerability scan workflow
daily-vul-scan.yml
using trivy-action created by the official Trivy team.This is the result of a test run.
2.
README.md
Add a badge to
README.md
to display the workflow results on the main branch.Sample:
The result is marked as failing due to vulnerabilities.
ref. https://github.com/R-HNF/gatling-operator/tree/add_daily-vul-scan
3.
trivy-results.tpl
Add a template
trivy-results.tpl
for writing out Trivy results to an issue.This is the sample of a test run.
Checklist
Please check if applicable
Relevant issue #45